Skip to content

Wait for readiness before bootstrap app jobs - #283

Closed
hamzamerzic wants to merge 2 commits into
mobius-os:mainfrom
hamzamerzic:fix/bootstrap-readiness-reviewed
Closed

Wait for readiness before bootstrap app jobs#283
hamzamerzic wants to merge 2 commits into
mobius-os:mainfrom
hamzamerzic:fix/bootstrap-readiness-reviewed

Conversation

@hamzamerzic

Copy link
Copy Markdown
Collaborator

Summary

  • add a bounded readiness wait to the shared app-job runner
  • use that wait only for initialization jobs launched during bootstrap
  • keep interactive installs, cron, and Run now immediate
  • preserve the install-source discriminator separately from the app source path

Credit

Builds on and supersedes #266 by @rgjordana. Their original readiness boundary and runner work is preserved; the follow-up fixes the inactive source comparison and adds install-path coverage.

Validation

  • pytest -q backend/tests/test_app_jobs.py backend/tests/test_app_capabilities.py — 24 passed
  • Python compilation for the runner, launcher, and installer
  • git diff --check
  • full source diff privacy review

rgjordana and others added 2 commits July 27, 2026 21:25
Co-authored-by: Möbius Agent <mobius-agent@users.noreply.github.com>
Keep the install source separate from the app source path and prove the bootstrap launch passes wait_for_ready while the existing interactive install remains immediate.\n\nCo-authored-by: Möbius Agent <mobius-agent@users.noreply.github.com>
@hamzamerzic

Copy link
Copy Markdown
Collaborator Author

Merged to main as part of #304. This corrected readiness implementation replaces the flawed install-path behavior identified in #266.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bug Something isn't working

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants